Method and apparatus for operating an electronic device in a low power mode

ABSTRACT

An electronic device, such as a hand-held portable computer, is provided with capability to operate an application during a low power mode. During the low power mode, portions of hardware, software, services, and/or other components of the portable computer that are not necessary to the operation of the application is suspended or otherwise deactivated. As each task is performed by the application, the components that are no longer needed for subsequent tasks to be performed by the application are also deactivated and reactivated as needed. The deactivation can be performed in sequence from the highest-level components to the lowest-level components to ensure that components that are needed by other components are not prematurely deactivated. A specific set of events transitions the portable computer out of the low power mode.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims the benefit under 35 U.S.C. § 119(e) ofU.S. Provisional Patent Application Ser. No. 60/504,165, entitled“SOFTWARE AND HARDWARE FEATURES FOR MINI-PC,” filed Sep. 18, 2003,assigned to the same assignee as the present application and which isincorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to electronic devices, and inparticular but not exclusively, relates to an electronic device, such asa hand-held portable computer, that has the capability to runapplications while in a low power mode.

BACKGROUND INFORMATION

Today's computer users are highly mobile individuals. Whether onbusiness trips, on vacations, or coming to and from work, theseindividuals are readily identifiable by their use of laptops,enhanced-functionality cellular telephones, Palm Pilots™, Blackberries™,and other portable electronic devices. Indeed, many establishmentsprovide Internet connections that cater to individuals who may be merelypassing through the establishment for a short period of time and whorequire a network connection. For instance, Internet connections areavailable at airports and hotels, and even in restaurants and coffeeshops.

Because of the portable nature of the electronic devices, there arecertain limits to their capabilities. Power consumption is one of theprime examples. Power consumption is generally a minor issue in anoperating environment where the user has “plugged” the electronic deviceinto an electrical power outlet or has docked the electronic device intoa docking station. In these situations, there is constant andsubstantially unlimited power for operating the electronic device,thereby eliminating the need for the electronic device to consume powerfrom an internal power source, such as an internal battery, whileplugged in.

However despite the proliferation of establishments that provideInternet connections (and typically a corresponding stationary powersupply), there are still many instances when a stationary power supplyis unavailable to the highly mobile user. In these instances, theelectronic device needs to rely on its internal battery to supply thepower necessary to run applications or to perform other functions withthe electronic device.

If operated in a full power mode using power from the internal battery,the electronic device can generally operate for only a few hours beforethe battery is drained. In fact, many different software services,software applications, and hardware can run concurrently in the fullpower mode using various subsystems and components in the electronicdevice. A display, disk drive, and processor (especially a graphicsprocessor) are some of the components of an electronic device that canrun concurrently, yet consume a substantial amount of power.

To help reduce power consumption, especially when a stationary powersupply is unavailable, many electronic devices include a “standby” modein which the electronic device turns OFF and/or substantially reducespower to all of its subsystems and components. In such a standby mode, auser generally cannot use any applications unless the electronic deviceis switched from the standby mode to the full power mode. As such, itcan often be necessary for the user to make only limited and veryefficient use of the electronic device while it is in full power modewhen there are no available stationary power supplies. Furthermore, itmay even be necessary for the user to keep the electronic devicecompletely turned off or in a substantially non-functional standby modeas much as possible.

If the user fails to diligently conserve power in this manner, then theelectronic device will run out of power and become unusable until theuser can recharge or replace the internal battery and/or connect to astationary power supply. For instance, repeatedly accessing a hard diskdrive when running applications can dramatically reduce the amount ofavailable power that can be delivered from an internal battery. Theconstant need for software applications to access the hard disk drive isan important reason for limiting or eliminating the functionality of theapplications in the standby mode. This constrained operating environmentis inconvenient and impractical for a highly mobile user who may wish touse a portable electronic device for certain applications when there areno available stationary power supplies.

BRIEF SUMMARY OF THE INVENTION

One preferred aspect provides a method usable for an electronic device.The method includes monitoring for an event, and if the event isdetected, determining operating parameters of an application. Based onthe determined operating parameters, the method selectively deactivateselements of the electronic device and maintains active at least oneelement of the electronic device that is usable in connection withoperation of the application. The method operates the application in thereduced power state of the electronic device using at least the activeelement of the electronic device.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments are described with referenceto the following figures, wherein like reference numerals refer to likeparts throughout the various views unless otherwise specified.

FIG. 1 is a front, top right isometric view of an example electronicdevice, which in this case is in the form of a hand-held portablecomputer including a lid shown in an open position.

FIG. 2 is a front, top right isometric view of the example hand-heldportable computer of FIG. 1 including the lid shown in a closedposition.

FIG. 3 is a block diagram of an embodiment of the portable computer anda representative operating environment in more detail.

FIG. 4 is a diagrammatic representation of power states in accordancewith one embodiment.

FIG. 5 is a diagrammatic representation of interaction and operation ofvarious components of the portable computer in view of the power statesof FIG. 4, according to one embodiment.

FIG. 6 is a flowchart of a technique for operating the portable computerin a low power mode in accordance with one embodiment.

DETAILED DESCRIPTION

Embodiments of techniques to operate an electronic device, for example,a portable electronic device in the form of a hand-held portablecomputer in a low power mode are described herein. In the followingdescription, numerous specific details are given to provide a thoroughunderstanding of embodiments. The invention can be practiced without oneor more of the specific details, or with other methods, components,materials, etc. In other instances, structures, materials, or operationsare not shown or described in detail to avoid obscuring aspects of theinvention.

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrases “in oneembodiment” or “in an embodiment” in various places throughout thisspecification are not necessarily all referring to the same embodiment.Furthermore, the particular features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments.

As an overview, an embodiment provides an electronic device withcapability to operate an application during a low power mode. Anon-limiting example of such an electronic device is a portableelectronic device. The electronic device, according to one embodiment,comprises a hand-held portable computer. During operation of theportable computer in the low power mode, hardware, software, services,and/or other components of the portable computer that are not necessaryfor operation of the application are suspended or otherwise deactivated.Furthermore, as each task is performed by the application, thecomponents that are not needed for subsequent tasks are deactivated andreactivated as needed. The deactivation can be performed in sequencefrom the highest-level components to the lowest-level components toensure that components that are needed by other components, or that areotherwise involved in operating dependencies with other components, arenot prematurely deactivated. A specific set of events transitions theportable computer out of the low power mode into some other operatingmode, such as a full power mode.

FIGS. 1-2 show front, top right isometric views of an example electronicdevice, in this case a hand-held portable computer 100 in which anembodiment may be implemented. While the portable computer 100 is usedas the illustrative example throughout this application, otherembodiments may be implemented with devices that may not necessarily bethought of as a “computer” or with devices that may not necessarily havethe same shape and appearance as the portable computer 100 illustratedin FIGS. 1-2. Examples include but are not limited to wirelesscommunication devices, display devices, monitors, audiovideo equipment,consumer electronic devices, or other electronic device that can havepower consumption issues that are addressable by the principlesdescribed herein.

As shown, the portable computer 100 is similar in appearance to a laptopcomputer, in that it comprises first and second portions 102 and 104,respectively, which are hinged. The first portion 102 can include akeypad or keyboard 110 and housing for the internal electroniccomponents (such as one or more processors, machine-readable storagemedia, graphics drivers, and so forth). The second portion 104 operatesas a lid that folds over the first portion 102 (when in a closedposition, such as shown in FIG. 2), and includes a display screen 108for displaying information or for otherwise presenting data (such as anemails, user interfaces, graphics, and the like) while the secondportion 104 is unfolded to an upright position as shown in FIG. 1.

Unlike a conventional laptop computer, however, the portable computer100 of one example embodiment is substantially smaller in size in termsof both volume and weight. For example, the portable computer 100 may be140 mm long, 101 mm wide, and 30 mm thick (while closed), with a weightof approximately one pound. The display screen 108 on the second portion104 may have a resolution comparable to a desktop computer monitor. Ingeneral, the size of the display screen 108, the size of the internalcomponents (e.g., chips and circuit boards) located within the firstportion 102, and the strategic placement of the internal components(e.g., density), and other factors will influence the overall formfactor of the portable computer 100. As illustrated in FIGS. 1-2, theportable computer 100 has a size such that it can be held securely in ahand 106 of a user whether in the open or closed position. In anotherembodiment, the portable computer 100 may have a larger or otherwisedifferent form factor and/or have a greater weight.

In one specific embodiment shown in FIG. 2, the portable computer 100can include a low power display 114 integrated within the second portion104. In such an embodiment, the low power display 114 can be used topresent certain information while the lid of the portable computer 100is closed and the portable computer 100 is in the low power mode, or beused to present other forms of data. The low power display 114 alsoincludes a user interface through which the user can interact with lowpower mode applications, trigger the portable computer 100 to transitionto the low power mode, and other operations.

While the low power display 114 is depicted in FIG. 2 as beingpositioned on the surface of the second portion 104, the low powerdisplay 114 may be positioned elsewhere on the portable computer 100.For example, the low power display 114 may be positioned on sidesurfaces, the bottom surface, or any combination of surfaces of theportable computer 100.

In one embodiment that will be described below, the portable computer100 of FIG. 1 includes a lid switch 112. The lid switch 112 operates asa type of trigger to indicate whether the lid of the portable computer100 is open or closed. Thus, for example, when the lid of the portablecomputer 100 is closed as shown in FIG. 2, the lid switch 112 can makephysical contact with an electromechanical connection, can changeorientation, can be depressed, or experience any other type of change instate that causes a signal such as an interrupt to occur. Such aninterrupt can be used by an operating system, a basic input/outputsystem (BIOS), a service, or other software component to initiate atransition from one power state to another power state (e.g., to the lowpower mode). The lid switch 112 can be embodied with any suitable shape,mechanism, functionality, or other operating feature.

Examples of the portable computer 100 in which embodiments of the lowpower mode techniques may be implemented are disclosed in U.S. patentapplication Ser. No. 10/338,802, entitled “SYSTEM AND METHOD FOR HEATREMOVAL FROM A HAND-HELD PORTABLE COMPUTER WHILE DOCKED”; U.S. patentapplication Ser. No. 10/338,815, entitled “NAVIGATION AND SELECTIONCONTROL FOR A HAND-HELD PORTABLE COMPUTER”; U.S. patent application Ser.No. 10/338,761, entitled “HEAT DISSIPATION FROM A HAND-HELD PORTABLECOMPUTER”; and U.S. patent application Ser. No. 10/338,791, entitled“KEYBOARD WITH MOUSE FOR A HAND-HELD PORTABLE COMPUTER”, all filed Jan.7, 2003, assigned to the same assignee as the present application, andall of which are incorporated herein by reference in their entireties.

FIG. 3 and the accompanying discussion provide a description of asuitable computing environment in which embodiments can be implemented.Although not required, embodiments will be described in the generalcontext of hardware and computer-executable instructions, such asprogram application modules, objects, drivers, services, or macros beingexecuted by a computer (such as by the portable computer 100). Inaddition to the embodiment shown in this figure, other embodiments canbe practiced with other computer systems and/or network configurations.

FIG. 3 shows a computing system 300, and in particular shows anembodiment of the portable computer 100 in more detail. The computingsystem 300 includes the portable computer 100 and a server computingsystem 302. The server computing system 302 may be located at one ormore network locations, for example, at one or more Internet ServiceProvider (ISP) locations to store and serve email information and toserve other information for the portable computer 100.

The portable computer 100 includes a high-power processing unit 304 forhigh-power processing, at least one system memory 306, and a system bus308 that couples various system components including the system memory306 to the high-power processing unit 304. The high-power processingunit 304 may be any logic processing unit, such as one or more centralprocessing units (CPUs), digital signal processors (DSPs), graphicsprocessors, application-specific integrated circuits (ASICs), etc.

In an embodiment, the portable computer 100 may also include a low-powerprocessing unit 310 for low power processing, and which may or may notnecessarily operate with the same operating system as the high-powerprocessing unit 304. For example, in one embodiment separate operatingsystems, memory, applications, or other components can be provided forthe high-power processing unit 304 and for the low-power processing unit310. It is also possible in an embodiment for the high-power processingunit 304 and for the low-power processing unit 310 to share certaincomponents, rather than having separate dedicated components.

The system bus 308 can employ any suitable bus structure orarchitecture, including a memory bus with memory controller, aperipheral bus, and a local bus. The system memory 306 may include oneor more read-only memories (ROM) 310 and one or more random accessmemories (RAM) 312. In one embodiment, separate ROM 310, RAM 312, and/orother memory can be dedicated for the low power display 114. A BIOS 314,for example, which can be stored in the ROM 310, contains routines thathelp transfer information between elements within the portable computer100, such as during start-up. Operation of an embodiment of the BIOS 314in connection with a low power mode will be described in further detailbelow.

The portable computer 100 may include a hard disk drive 316 for readingfrom and writing to a hard disk 318. The hard disk drive 316communicates with the high-power processing unit 304 via the system bus308. The hard disk drive 316 may include interfaces or controllers (notshown) coupled between such drive(s) and the bus 308. The hard diskdrive 316 and its associated hard disk 318 provide nonvolatile orotherwise persistent storage of computer readable instructions, datastructures, program modules and other data for the portable computer100. Although the depicted portable computer 100 employs the hard diskdrive 316 and the hard disk 318, other types of drives andcomputer-readable media that can store data accessible by a computer maybe employed, such as compact disks (CDs), magnetic cassettes, flashmemory cards, digital video disks (DVDs), Bernoulli cartridges, RAMs,ROMs, smart cards, etc. In one embodiment, the hard disk drive 316and/or other drives are not integrated within a housing of the portablecomputer 100 itself, but instead are external devices that areaccessible via hardwire or wireless communication interfaces.

The system memory 306 can be used for storing various program modules,such as one or more operating systems 320, one or more applicationprograms 322 (such as an email program, a media player, or otherapplications that can operate in a high power mode or in a low powermode), other programs or modules 324, and program data 326. Anon-limiting example of an operating system 320 that may be used isWindows XP™, which is commercially available from Microsoft Corporationof Redmond, Wash. Windows XP™ as well as other suitable operatingsystems used with certain embodiments may include a power managementsubsystem. In an embodiment, power management capabilities are providedin connection with a low power mode that supplements power managementprovided by the power management subsystem of the operating system 320.

The program data 326 can be stored as a data structure, file, or otherdata format in a cache, database, or other storage unit integrated in orseparate from the system memory 306. In one embodiment, the program data326 includes power profiles and other power management data indicativeof the power requirements of particular services, software, and hardwareof the portable computer 100. As will be described later, this powermanagement data is used in one embodiment to determine which componentof the portable computer 100 to keep “ON” or to turn “OFF” during thelow power mode, length of time to keep ON or OFF, sequence of turningvarious components ON or OFF, and other parameters and settings. Furtherdetailed discussion of the various other programs/modules 324 thatinteract for managing and controlling operations in the low power modeand of the application program 322 (and more specifically, some type ofsuitable low power mode application program) will be provided below.

The portable computer 100 may also include a web browser 328 forpermitting the portable computer 100 to access and exchange data withsources such as Internet web sites, corporate intranets, extranets,and/or other networks as described below, as well as other serverapplications on server computers. For purposes of clarity the browser328 is shown separately in FIG. 3. According to various embodiments, thebrowser 328 can comprise one of the application programs 322, one of theother programs/modules 324, and/or may be integrated in some manner withthe operating system(s) 320. While shown in FIG. 3 as being stored inthe system memory 306, the operating systems 320, application programs322, other programs/modules 324, program data 326, and browser 328 canbe stored on the hard disk 318 of the hard disk drive 316 and/or othercomputer-readable media in another embodiment. Moreover, the variouselements depicted as being stored in the system memory 306 need notnecessarily reside on the same physical memory. For example, inembodiments where the low-power processing unit 310 and the low powerdisplay 114 can be operatively detached from the portable computer 100or otherwise operate independently of other components of the portablecomputer 100, separate memory (having an operating system, RAM, ROM,applications, and other elements stored thereon) can be operativelydecoupled from the portable computer 100 along with the low-powerprocessing unit 310 and the low power display 114. In such anembodiment, the decoupleable components can be integrated in a low powerdisplay module (LPDM).

A user can enter commands and information into the portable computer 100through one or more input devices (such as the keyboard 110) and apointing device (such as a mouse 330 that may be, for example, builtinto the keyboard 110, an example embodiment of which is disclosed inU.S. patent application Ser. No. 10/338,791), or through such othertypes of devices usable for providing user input. Alternatively oradditionally, the mouse 330 can be embodied as a touch pad as comparedto physical buttons. Another input device may take the form of one ormore buttons 332 on the side of the keyboard 110, with the button(s) 332usable for scrolling and clicking via turning and pressing of thebutton(s) 332. Other possible input devices can include a microphone,joystick, game pad, scanner, etc. (not shown). These and other inputdevices are connected to the high-power processing unit 304 through aninterface 334 such as a serial port interface that couples to the bus308, although the portable computer 100 may employ other interfaces suchas a parallel port, a game port or a wireless interface or a universalserial bus (USB). The interface 334 can be any suitable communicationinterface to the bus 308 and need not necessarily be a port per se. Inone embodiment, the input devices such as a mouse, joystick, game pad,keyboard, etc. are integrated directly into the housing of the portablecomputer 100, rather than or in addition to being coupleable via aserial or parallel port interface.

The display screen 108 operates as the main display and is coupled tothe bus 308 via a graphics interface 336, such as a video adapter orother graphics component that will allow video and other graphics to berendered on the display screen 108. The low power display 114 may alsobe present in one embodiment to allow presentation of data (e.g.,presentation on the outside surface of the second portion 104 of theportable computer 100) during the low power mode, when the lid is closedon the portable computer 100. The low power display 114 may be coupledto the bus 308 by way of the graphics interface 336 (or other interface)or may be directly coupled to the bus 308. The low power display 114 canbe provided with its own user interface, such as buttons and menus. Alsoas depicted in FIG. 3, the lid switch 112 can be coupled to the systembus 308 to allow the various components of the portable computer 100 todetect and respond to a closing or opening of the lid of the portablecomputer 100.

The portable computer 100 can operate in a networked environment usinglogical connections to one or more remote computers and/or devicesexternal to the portable computer 100, such as the server computingsystem 302 and a network device 340, such as a printer or networkstorage unit. The portable computer 100 is logically connected to one ormore remote computing systems or devices under any suitable method ofpermitting computers to communicate, such as through a wireless localarea network (WLAN) 342, a wireless wide area network (WWAN), or anyother network 344, including wired and wireless networks that use or cancommunicate with the Internet (e.g., World Wide Web). Variousembodiments can be implemented to communicate with several types ofcommunication networks, including but not limited to, telecommunicationsnetworks, cellular networks, paging networks, wired and wirelessenterprise-wide computer networks, intranets, extranets, the Internet,and other types of networks. Examples of wireless systems and protocolswith which the portable computer 100 can communicate, include but arenot limited to, Wi-Fi, Bluetooth, 802.11, and others.

When used in a LAN networking environment, the portable computer 100 canbe connected to the LAN 342 through an adapter or network interface 346(communicatively linked to the bus 308). When used in a WWAN or othernetwork 344, the portable computer 100 may include a modem, transceiver348 or other device, such as the network interface 346, for establishingcommunications over this networking environment or for otherwisecommunicating with external devices. The transceiver 348 as shown inFIG. 3 is communicatively linked between the interface 334 and thenetwork 344. The transceiver 348 may be one or more transmitters,receivers, or other communication devices that are compliant with, forexample, 802.11, GPS, Bluetooth, cellular (TDMA, FDMA, and/or CDMA),Wi-Fi, virtual private network (VPN), and/or other communicationstandards or techniques.

In one embodiment, the portable computer 100 is communicatively linkedto the server computing system 302 through the LAN 342 and/or thenetwork 344 with transmission control protocol/Internet protocol(TCP/IP) middle layer network protocols or other network protocollayers, such as User Datagram Protocol (UDP). The network connectionsshown in FIG. 3 are only some examples of establishing communicationlinks between computers, and other links can be used, including bothhardwire and wireless links.

The server computing system 302 includes one or more servers 350. In thecontext of email, the server 350 can comprise an email server. Anexample of such a server is a Microsoft Exchange™ server, and theprinciples described herein are not to be limited to only emailimplementations that use a Microsoft Exchange™ server.

FIG. 4 is a diagrammatic representation 400 of power states inaccordance with one embodiment. More particularly, FIG. 4 showsoperating power states S0-S2 and S3-S5 that are supported by theAdvanced Configuration and Power Interface (ACPI) specification and anon-ACPI-defined low power mode state S2.5 in accordance with oneembodiment. Typically, the S0-S2 and S3-S5 power states are defined inpower profiles that are integrated as part of a power managementsubsystem (such as a Windows power management subsystem) in theoperating system 320. For the sake of brevity, only a summary of theACPI power states will be provided herein. Further details of the ACPIpower states can be found in Compac Computer Corporation et al.,“Advanced Configuration and Power Interface Specification,” Revision2.0c, Aug. 25, 2003. Moreover, another embodiment can be based on powerstates that are not necessarily compliant with the ACPI specification.

In the S0 power state, the high-power processing unit 304 is executinginstructions at its full clock speed, and the portable computer 100 isotherwise operating at substantially full (e.g., 100%) capacity. Forinstance, many services are operational and performing their tasks, datais being written to and read from the hard disk drive 316, the maindisplay screen 108 is rendering content, and other working state tasksare being performed.

The S1 power state is a sleeping-low wake mode. In the S1 power state,the high-power processing unit 304 (or other processing unit) is notexecuting instructions. Processor context is maintained, and all systemclocks and memory are in refresh. The S2 power state is also asleeping-low wake mode that is logically lower than the S1 power state,and is assumed to conserve more power. The processor context is notmaintained, and the clock of the high-processing unit 304 is stopped.Moreover, all system clocks, cache(s) and memory are in refresh, and allpower resources that supply a system-level reference of S0 or S1 are inthe OFF state. The S1 and S2 power states are low wake modes in that anyinterrupt (such as the pressing of a key on the keyboard 110) generallyawakens or transitions the portable computer 100 from these modes.

The S3 power state is a standby mode and is logically a lower powerstate than the S2 power state. Memory is continuously running andrefreshed, and so the data context of the RAM 312 is maintained, forinstance. However, the high-power processing unit 304, componentsassociated with the graphics system, the hard disk drive 316, the maindisplay screen 108, and other components of the portable computer 100are turned OFF and no services are running. In one embodiment, a fewspecific actions awaken the portable computer 100 from the S3 powerstate, such as pressing a power button, opening the lid of the portablecomputer 100 (thus activating the lid switch 112), and the receipt of awake-on-LAN/USB/fax signal.

In the S4 power state, the portable computer 100 is in a hibernate mode.The data context of the RAM 312 is not maintained, and most componentsare turned OFF and not running. The S5 power state is logically thelowest power state, and is a soft OFF mode that requires a completeboot-up when awakened.

In accordance with an embodiment, an intermediate power state isprovided between the S2 and S3 power states. This is a low power modeand non-ACPI-defined power state, which is labeled in FIG. 4 as thepower state “S2.5.” The label “S2.5” is used herein merely for the sakeof convenience and ease of explanation and to provide context, and isnot intended to limit the invention to strictly an ACPI environment.

In an embodiment of the S2.5 power state, most of the components of theportable computer 100 are turned OFF. However, a low power modeapplication is operating, and the various components of the portablecomputer 100 that are required to support operation of that low powermode application are selectively ON or otherwise running, until suchcomponents are no longer needed during operation of the low power modeapplication (in which case such components are then turned OFF). Thespeed of the clock in the high-power processing unit 304 is also reducedto a minimum low speed to support the low power mode application. Forinstance, the speed of the clock during the low power mode can be set toa minimum speed that is specified for the high-power processing unit304, a non-limiting and purely illustrative example of which isapproximately 433 MHz. As such, for transitioning to and operating inthe S2.5 power state, the sequence and duration of turning OFF certainunnecessary components can minimize power consumption. Moreover, theportable computer 100 will not be awakened from the S2.5 power state byany basic interrupt (as contrasted with the S1 or S2 power states).Rather, only specific events will cause a transition to a higher powerstate (e.g., S0), such as opening the lid of the portable computer 100.Further details of low power mode operation in the S2.5 power state,including transitioning to and from the low power mode, are providedbelow.

FIG. 5 is a diagrammatic representation 500 of interaction and operationof various components of the portable computer 100 in view of the powerstates of FIG. 4, according to one embodiment. More particularly, thediagrammatic representation 500 illustrates operation in the low powermode (i.e., the S2.5 power state) in more detail.

The BIOS 314 includes a real time clock (RTC) 502, a bootloader 504, anda CPU minimum clock and throttle 506. According to one embodiment, theBIOS 314 includes a low power mode subsystem 508, which interacts withother low power mode components to control and manage transition to andfrom the S2.5 power state, and to manage and control the turning ofcertain components (generally hardware-related components) OFF or ON inconnection with low power mode operation. The low power mode subsystem508 can be embodied in software source code, software object code, orother machine-readable instructions. Furthermore, the BIOS 314 cancontrol and manage transitions into and out of the S0 and S3 powerstates, as indicated in FIG. 5.

Transitioning or otherwise entering into the S2.5 power state (or alsoentering the S3 power state) according to one embodiment can beperformed by closing the lid of the portable computer 100, therebytriggering or otherwise activating the lid switch 112. Additionally,exiting the S2.5 power state (or also exiting the S3 power state) can beperformed by opening the lid of the portable computer 100, which alsotriggers a change in state of the lid switch 112. An arrow 516 in FIG. 5represents the entering into and exiting from the S2.5 power state. Thearrow 516 indicates that the entering/exiting may be performed by a BIOScall, an interrupt, or other communication to the BIOS 314 from the lidswitch 112. When entering the low power mode of the S2.5 power state,the low power mode subsystem 508 of the BIOS 314 then wakes up a lowpower mode service 520 (indicated by an arrow 522). Alternatively oradditionally, a broken arrow 518 represents that the transition to orfrom the S2.5 power state can be performed by a direct communication (asa result of activation of the lid switch 112) to the low power modeservice 520 from the lid switch 112.

In an embodiment, entering the S2.5 power state also can be performedvia a low power display module (LPDM) 510 that includes the low powerdisplay 114. The LPDM 510 includes a user interface 512 (which can beembodied as controls, buttons, or menus on the low power display 114)that can communicate (indicated with an arrow 525) with the low powermode subsystem 508 of the BIOS 314 to initiate transition into the S2.5power state. Alternatively or additionally, the user interface 512 cancommunicate directly with the low power mode service 520 (alsorepresented by the broken arrow 518) to initiate transition into theS2.5 power state. Further alternatively or in addition, the LPDM 510(including its user interface 512) can communicate with an LPDMapplication service 524 (indicated by an arrow 526) to initiatetransition into the S2.5 power state or to otherwise present informationduring the low power mode (such as playing of media files orpresentation of email on the low power display 114). A user 514 canoperate the lid switch 112 or the LPDM 510 to trigger transition into anapplicable power state.

The low power mode service 520 of one embodiment comprises a service,program, subroutine, module, or other software code or set ofmachine-readable instructions that is always running. In the S0 powerstate, the low power mode service 520 is running but is basicallyperforming a minimal amount of tasks, or more specifically, the lowpower mode service 520 is monitoring for certain activities that signala need to transition to the S2.5 power state. An example of such amonitored activity is activation of the lid switch 112, which indicatesa closing or opening of the lid of the portable computer 100.

When the lid is closed or some other activity signals a need totransition to the low power mode of the S2.5 state, the low power modeservice 520 wakes up or otherwise becomes more active, and determineswhich low power mode application is to be made active in the low powermode (if any); determines the hardware, software, and power needs forthat low power mode application from information provided by the lowpower mode application and/or from power profiles comprising part of theprogram data 324; communicates with either or both the BIOS 314 or withan operating system kernel 528 (as indicated by an arrow 532) to turncertain elements OFF in a specific sequence; or otherwise performs tasksassociated with operating the portable computer 100 in the low powermode. The arrow 522 also represents this communication to the BIOS 314by the low power mode service 520, and an arrow 532 represents thecommunication to the operating system kernel 528 by the low power modeservice 520. The operating system kernel 528 and/or the BIOS 314 canthen selectively begin powering down unnecessary hardware, software,services, and other elements. In the context of email in one embodiment,the arrow 522 also represents the turning ON and OFF of the low powermode subsystem 508 of the BIOS 314, to allow activation and deactivationof elements of the portable computer 100 (such as the transceiver 348)that are used for periodic polling of an external server (such as theserver 350) for new email.

In an embodiment, the low power mode service 520 sends asuspend-until-resume (as compared to suspend-until-interrupt) message toeither or both the operating system kernel 528 and the BIOS 314, so asto suspend tasks that are not needed, unused, or otherwise irrelevantduring the low power mode. When a resume signal is sent from the lowpower mode service 520, the suspended tasks are resumed from the pointwhere they were suspended. It is noted that an embodiment removes thesetasks from suspension with a resume signal, as compared to an interrupt.An interrupt often removes elements from a standby state in existingsystems. However, with an embodiment, interrupts are generated whileoperating in the low power mode, and therefore, resume signals ratherthan interrupts are used to remove elements from suspension to ensurethat such elements remain suspended during the low power mode and do notperform unnecessary tasks (and therefore unnecessarily consume power).

The low power mode service 520 can comprise part of the program/modules324 shown in FIG. 3. In one embodiment, the low power mode service 520comprises a service that can be written using the Microsoft Win32Software Development Kit (SDK), so as to allow the service to interactand interface with the operating system kernel 528. The operating systemkernel 528, such as a Windows XP™ kernel, can in turn comprise part ofthe overall operating system 320.

In the case of the operating system kernel 528, it can make calls to theBIOS 314 to turn ON or turn OFF certain elements during the S1-S5 powerstates, as represented by an arrow 530. In one embodiment, this includesdirect BIOS calls to the low power mode subsystem 508 to turn OFFcertain hardware elements that are not necessary for the low power mode.Alternatively or additionally, the operating system kernel 528 can turnOFF certain software elements, such as unnecessary services 536 orapplications, by turning OFF their corresponding drivers 534. Theoperating system kernel 528 can also selectively turn ON such services536 or applications by activating their drivers 534.

In an embodiment operating in the low power mode, the low power modeservice 520 and/or the LPDM application service 524 interacts with oneor more low power mode applications 538 (indicated as low powerapplications A and B in FIG. 5). An example of the low power applicationA is a media player, such a low power media player disclosed in U.S.application Ser. No. ______, Attorney Docket No. 930086.411, entitled“LOW POWER MEDIA PLAYER FOR ELECTRONIC DEVICE,” and filed ______. Anexample of the low power application B is a client-side email program,such as disclosed in U.S. application Ser. No. ______, Attorney DocketNo. 930086.407, entitled “METHOD AND SYSTEM FOR MANAGING EMAILATTACHMENTS FOR AN ELECTRONIC DEVICE,” filed May 7, 2004; U.S.application Ser. No. ______, Attorney Docket No. 930086.408, entitled“METHOD AND SYSTEM FOR POLLING AND CACHING EMAILS FOR AN ELECTRONICDEVICE,” filed May 7, 2004; and U.S. application Ser. No. ______,Attorney Docket No. 930086.409, entitled “METHOD AND SYSTEM FOR EMAILSYNCHRONIZATION FOR AN ELECTRONIC DEVICE,” filed May 7, 2004. All ofthese patent applications are assigned to the same assignee as thepresent application and are incorporated herein by reference in theirentireties.

There may also be some type of network access component 540 (either orboth wireless or wired) that can be selectively activated during the lowpower mode. Examples of the network access component 540 include thetransceiver 348 or the network interface 346. The low power modeapplications 538 and the network access component 540 can access a diskcache 542 or other suitable volatile memory location as needed duringthe low power mode, wherein the disk cache 542 can comprise part of theRAM 312 or other storage unit.

The low power mode applications 538 can communicate with installedapplications 548 and 556 during the low power mode. Examples of theseinstalled applications include Windows Media Player™ 9 and MicrosoftOutlook™ 2003. In an embodiment, these installed applications 548 and556 provide supporting functions and data for the low power modeapplications 538 during the low power mode. As an example, if theinstalled application 556 is Windows Media Player™ 9, then the low powerapplication A (e.g., a low power media player) can interact with theinstalled application 556, via an application program interface (API)544 or other suitable means for communicating information between thelow power media player 538A and the installed application 556, to usethe play, stop, fast forward, pause, rewind, or other functions of theinstalled application 556. An arrow 552 represents this interaction. Useof these existing functions of the installed application 556 by oneembodiment avoids the need to create code for the low power applicationA to perform the same functions.

Information such as playlists, songs, titles, artists, time, etc. ismaintained by the installed application 556 (depicted by an arrow 550)in one or more libraries 546, which is in turn accessible by the lowpower application A. Arrows 554 and 526 represent that this libraryinformation can be forwarded by the low power application A to the LPDMapplication service 524 and then to the LPDM 510 for presentation on thelow power display 114. Thus, an embodiment of the LPDM applicationservice 524 is usable for communicating information between the lowpower media player 538A and the LPDM 510.

FIG. 6 is a flowchart 600 of a technique for operating the portablecomputer 100 in the low power mode or other reduced power state inaccordance with one embodiment. Features represented by the flowchart600 can be embodied in software source code, software object code, orother machine-readable instructions stored on a machine-readable medium.For example, some operations depicted in the flowchart 600 can beperformed by the low power mode service 520 embodied as software code inthe system memory 306 and using power management data stored therein orin some other storage location of the portable computer 100. The variousoperations need not necessarily be performed in the exact order shown,and that some operations can be added, removed, modified, or combined.

Beginning at a block 602, power management data determination isperformed. In this operation, applications that are to be made availablein the low power mode are first identified (e.g., the low power modeapplications 538). Next, the specific power, hardware, and softwarerequirements or other operating parameters for these applications aredetermined. For example for a low power MP3 player, a wireless 802.11network connection is not needed or is otherwise irrelevant, andtherefore the associated modem hardware and software can be selected fordeactivation during the low power mode. However, such modem hardware andsoftware may be needed by an email application program, and therefore,this modem hardware and software are not selected for deactivation ifthe email application program is to be used in the low power mode.Certain elements, such as the main display screen 108 can be selectedfor deactivation, since the lid of the portable computer 100 isgenerally closed during the low power mode.

Additional information that can be determined at the block 602 includesminimum processor speed for an application, minimum power consumptionfor certain tasks, supporting services that run and when such servicesare to be running, which peripheral devices and supporting hardware andsoftware can be deactivated when using a particular low power modeapplication, and so on. Additionally, determination is made of certainprocessor threads or tasks that can be suspended (to ensure that thesetasks are not performed during the low power mode), and then resumedwhen the low power mode is exited. Also, a proper sequence of turningOFF certain elements can be determined and set. For instance, thehighest-level components are to be turned OFF by one embodiment beforethe lowest-level components are turned OFF (e.g., a disk drive is notturned OFF until the services that are using the disk are turned OFF).Many different pieces of information may be determined at the block 602,and may vary from one application or implementation to another.

This power management data can comprise part of a power profile for eachof the low power mode applications. In one embodiment, such powermanagement data can be determined at the block 602 during a preliminarydesign phase or through circuit or software simulation testingtechniques. The power management data can then be stored in tables,coded into software (including coding into the low power modeapplications themselves), embodied as fixed or variable code, or storedin some other data structure format that allows such information to belater accessed during actual operation of the portable computer 100. Thepower management data can comprise the program data 326 in the systemmemory 306, can be stored in the hard disk drive 316, or can be storedas data in some other suitable storage location.

At a block 604, the portable computer 100 operates in a non-low powermode. For instance, the portable computer 100 may be fully operating inthe S0 power state or may be sleeping in the S1-S2 power states. Duringthe block 604 according to one embodiment, the low power mode service520 or the low power mode subsystem 508 in the BIOS 314 is alwaysrunning in the background and monitoring for events at a block 606. Morespecifically according to an embodiment, the low power mode service 520or the low power mode subsystem 508 is used for monitoring or otherwisedetermining activity from the lid switch 112, activity from the LPDM510, or other user-initiated action that is indicative of the user's 514desire to operate the portable computer 100 in the low power mode.

If no event is detected at a block 608, then the monitoring continues atthe block 606. However, if one of the specified events is detected atthe block 608, then the low power mode service 520 is given control bythe BIOS 314 and by the operating system kernel 528, and checks whethera low power mode application 538 is present at a block 610 or isotherwise requested to perform a task during the low power mode. If thelow power mode application 538 is not present or is otherwise notrequested to perform a task, then the portable computer 100 transitionsto the standby mode at a block 612, such as the S3 power state. The BIOS314, in one embodiment, can initiate the transition to the S3 powerstate at the block 612.

If the low power mode service 520 determines at the block 610 that thelow power mode application 538 is present and is designated to perform atask during the low power mode, then the low power mode service 520obtains the power management data associated with that low power modeapplication 538 at a block 614. Obtaining this data can be performed bycalling the particular low power mode application 538 and obtaining thedata therefrom, or by independently accessing a data store. In oneembodiment, the power management data can be obtained at boot-up fromthe BIOS 314, rather than at the block 614 after the portable computer100 has been operating in a non-LPM mode.

Based on the obtained power management data, the low power mode service520 can be used for determining the power requirements and otheroperating parameters for the low power mode application 538 at the block616. The low power mode service 520 generates and sends instructions tothe operating system kernel 528 and/or to the BIOS 314 (via functioncalls, for instance) at a block 618. These instructions provideinformation that identifies portions of hardware, software, services,tasks, and the like for selective turn OFF, deactivation, or suspension,wherein such portions are unnecessary for operation of the low powermode application 538 during the low power mode. Furthermore, theseinstructions provided by the low power mode service 520 can specify aparticular sequence in which the portions are to be turned OFF.

The BIOS 314 and/or the operating system kernel 528 can be used in anembodiment for sequentially turning OFF, suspending, or otherdeactivating at a block 620, such as basing these actions on operatingdependencies between the various elements to be suspended, turned OFF,or otherwise deactivated. The operations at the block 620 also includereducing the speed of the processor clock. As the unnecessary elementsare turned OFF, suspended, or otherwise deactivated, the portablecomputer 100 thus transitions into the low power mode of the S2.5 state.The low power mode application 538 is called or otherwise activated at ablock 622 to begin performing one or more tasks in the low power mode.

As each task is performed and completed at the block 622, an embodimentof the low power mode service 520 checks to determine if certainelements or other resources associated with that particular task can beturned OFF as subsequent tasks are to be concurrently or subsequentlyperformed by the low power mode application 538. This updated checkingis represented in the flowchart 600 by iterative arrows that point fromthe block 622 back to either or both the blocks 614 and 616—if there areresources that can be turned OFF, then the operations in the blocks618-622 are repeated.

The low power mode service 520 monitors for an event at a block 624 thatsignals a request to exit the low power mode. For instance, opening thelid of the portable computer 100 activates the lid switch 112, whichcommunicates a signal to either the low power mode service 520 or to theBIOS 314 to exit the low power mode and return to the S0 power state. Ifsuch an event is detected at the block 624, then the low power modeservice 520 generates a resume message to the operating system kernel528 and/or to the BIOS 314, thereby allowing these components toun-suspend or otherwise activate previously deactivated hardware,software, services, tasks, and the like. Until such events are detected,the portable computer 100 continues operation in the low power mode atthe block 622.

All of the above U.S. patents, U.S. patent application publications,U.S. patent applications, foreign patents, foreign patent applicationsand non-patent publications referred to in this specification and/orlisted in the Application Data Sheet, are incorporated herein byreference, in their entirety.

The above description of illustrated embodiments, including what isdescribed in the Abstract, is not intended to be exhaustive or to limitthe invention to the precise forms disclosed. While specific embodimentsand examples are described herein for illustrative purposes, variousequivalent modifications are possible and can be made without deviatingfrom the spirit and scope of the invention.

For example, while some embodiments have been described in the contextof interacting with a Windows XP™ kernel and operating in conjunctionwith the power states defined in the ACPI specification, the inventionis not limited to these specific implementations. Other embodiments maybe implemented with electronic devices that use a different operatingsystem and/or that have power states defined using some otherspecification.

Moreover, various embodiments have been described wherein certaincomponents communicate with other components in a specific sequence toaccomplish a particular task. For instance, one embodiment has beendescribed above where the lid switch 112 communicates with the BIOS 314,which then communicates with the low power mode service 520 to wake upthat service. This is merely one example implementation, and there is norestriction to any particular communication sequence or restriction touse of only the specific components in the specific manner. Other routesof communications, other communication sequences and protocols, andother components may be used in various embodiments to wake up the lowpower mode service 520, or to accomplish other tasks.

These and other modifications can be made to the invention in light ofthe above detailed description. The terms used in the following claimsshould not be construed to limit the invention to the specificembodiments disclosed in the specification and the claims. Rather, thescope of the invention is to be determined entirely by the followingclaims, which are to be construed in accordance with establisheddoctrines of claim interpretation.

1. A method usable for an electronic device, the method comprising:monitoring for an event; if the event is detected, determining operatingparameters of an application; based on the determined operatingparameters, selectively deactivating elements of the electronic deviceand maintaining active at least one element of the electronic devicethat is usable in connection with operation of the application; andoperating the application in a reduced power state of the electronicdevice using at least the active element of the electronic device. 2.The method of claim 1 wherein the electronic device includes a switch toindicate whether a lid of the electronic device is either open orclosed, wherein monitoring for the event includes detecting a state ofthe switch that indicates whether the lid is closed.
 3. The method ofclaim 1 wherein the electronic device includes a low power displaymodule, wherein monitoring for the event comprises detecting whether arequest to transition to the reduced power state has been entered viathe low power display module.
 4. The method of claim 1, furthercomprising if the event is detected: determining whether there is arequest to perform a task with the application while in the reducedpower state; and if the request is determined to be absent, deactivatingelements of the electronic device including the element that is usablein connection with operation of the application in the reduced powerstate.
 5. The method of claim 1 wherein selectively deactivatingelements of the electronic device includes selectively deactivating theelements according to a sequence based at least in part on whichparticular element uses a particular resource at a particular time. 6.The method of claim 1 wherein selectively deactivating elementsincludes: communicating with an operating system kernel and specifyingwhich elements to deactivate; and deactivating the specified elementsusing the operating system kernel by deactivating drivers associatedwith the specified elements.
 7. The method of claim 1 whereinselectively deactivating elements includes: communicating with a basicinput output system (BIOS) and specifying which hardware-relatedelements to deactivate; and deactivating the specified hardware-relatedelements using the BIOS.
 8. The method of claim 1 wherein selectivelydeactivating elements includes generating a suspend-until-resume messageto suspend tasks, the method further comprising: generating a resumemessage to resume a suspended task at a point where the task wassuspended; and exiting the reduced power state.
 9. The method of claim1, further comprising: performing a task using the application programwhile the electronic device is in the reduced power state; determiningwhether resources associated with the task are relevant to perform someother task using the application program while the electronic device isin the reduced power state; and if at least some of the resources areirrelevant to performing the other task, deactivating such resources.10. The method of claim 1, further comprising obtaining the operatingparameters of the application, including any one or more of readingpower management data from a storage unit, obtaining the powermanagement data from the application, obtaining the power managementdata from fixed code, obtaining the power management data from variablecode, and obtaining the power management data from a basic input outputsystem (BIOS).
 11. A method usable for an electronic device, the methodcomprising: obtaining data indicative of parameters to operate anapplication during a low power mode of the electronic device; using theobtained data to selectively deactivate elements of the electronicdevice during the low power mode; maintaining at least one element thatis usable by the application during the low power mode activated whilesuch element is used by the application during the low power mode; anddeactivating such element otherwise during operation of the applicationin the low power mode.
 12. The method of claim 11, further comprisingsubstantially maintaining the deactivated elements deactivated duringthe low power mode until a transition to a higher power mode.
 13. Themethod of claim 11 wherein the elements to be deactivated are unused bythe application during the low power mode.
 14. The method of claim 11wherein selectively deactivating includes selectively deactivating theelements in a sequence from highest-level elements to lowest-levelelements.
 15. The method of claim 11, further comprising initiatingtransition to the low power mode in response to either one or both of aclosing of a lid of the electronic device and operating an interface ona low power display module.
 16. The method of claim 11 whereindeactivating elements of the electronic device includes communicatinginstructions to deactivate the elements to either one or both of anoperating system kernel and a basic input output system.
 17. The methodof claim 11 wherein deactivating elements of the electronic deviceincludes suspending tasks while in the low power mode, and resuming thetasks in response to a specific instruction rather than in response toan interrupt.
 18. The method of claim 11 wherein selectivelydeactivating the elements includes selectively deactivating in asequence from highest-level elements to lowest-level elements, includinginitially deactivating a first element whose operation depends on asecond element, and then deactivating the second element subsequent todeactivating the first element.
 19. A method usable for an electronicdevice, the method comprising: reducing power supplied to elements ofthe electronic device that are at least substantially unnecessary foroperation of an application during a low power mode of the electronicdevice; providing power to other elements of the electronic device at anamount that supports operation of the application during the low powermode of the electronic device; and selectively reducing power to atleast some of these other elements after such other elements are used bythe application in the low power mode.
 20. The method of claim 19wherein the power to at least some of the other elements, after suchother elements are used by the application in the low power mode, isreduced if such other elements are unused for subsequent operation ofthe application in the low power mode.
 21. The method of claim 19wherein reducing power to the elements of the electronic device includesinitially reducing power to high-level components and then sequentiallyreducing power to low-level components whose operation is independent ofoperation of the high-level components.
 22. The method of claim 19,further comprising presenting at least some data associated withoperation of the application in the low power mode in a low powerdisplay instead of in a main display screen.
 23. An article ofmanufacture usable for an electronic device, the article of manufacturecomprising: a machine-readable medium having instructions stored thereonto cause a processor to operate an application of the electronic devicein a low power mode, by: obtaining data indicative of parameters tooperate the application during the low power mode of the electronicdevice; using the obtained data to selectively deactivate elements ofthe electronic device during the low power mode; maintaining at leastone element that is usable by the application during the low power modeactivated while such element is used by the application during the lowpower mode; and deactivating such element otherwise during operation ofthe application in the low power mode.
 24. The article of manufacture ofclaim 23 wherein the machine-readable medium further includesinstructions stored thereon to substantially maintain the deactivatedelements deactivated during the low power mode until a transition to ahigher power mode.
 25. The article of manufacture of claim 23 whereinmachine-readable medium further includes instructions thereon toselectively deactivate the elements in a sequence from highest-levelelements to lowest-level elements, including instructions to initiallyreduce power to high-level components and sequentially reduce power tolow-level components whose operation is independent of operation ofrespective higher-level elements.
 26. The article of manufacture ofclaim 23 wherein the machine-readable medium further includesinstructions stored thereon to present information obtained by theapplication during its operation in the low power mode in a low powerdisplay of the electronic device, instead of presenting such informationon a main display screen.
 27. The article of manufacture of claim 23wherein the instructions to deactivate the elements include instructionsto suspend operation of the elements and resume operation in response toa resume message.
 28. A system usable for an electronic device, thesystem comprising: a means for monitoring for an event; a means fordetermining operating parameters of an application, if the event isdetected; a means for selectively deactivating elements of theelectronic device, based on the determined operating parameters, and formaintaining active at least one element of the electronic device that isused in connection with operation of the application; and a means foroperating the application in the reduced power state of the electronicdevice using at least the active element of the electronic device. 29.The system of claim 28 wherein the means for monitoring for the eventincludes either one or both of a means for determining if a lid of theelectronic device is closed and a means for determining if a request toenter the reduced power state is provided via a rear display module. 30.The system of claim 28, further comprising a means for sequentiallydeactivating the elements of the electronic device based on operatingdependencies between these elements.
 31. The system of claim 28, furthercomprising: a means for storing applications, program data, at least oneoperating system, and other information; a means for presenting data; ameans for communicating with devices external to the electronic device;a means for high-power and low-power processing; and a means forproviding user input.
 32. An apparatus, comprising: an application; atleast one component to provide an indication of a request to transitionto a low power mode; a basic input output system (BIOS) having a lowpower mode subsystem to receive the indication from the component and toinitiate transition into the low power mode; and a low power modeservice that can be activated by the low power mode subsystem, and toalternatively receive the indication from the component to initiate thetransition into the low power mode, the low power mode service beingfurther able to determine operating parameters of the application duringthe low power mode and to provide instructions to the low power modesubsystem to selectively deactivate elements based on the determinedoperating parameters.
 33. The apparatus of claim 32, further comprisingan operating system kernel to receive and respond to the instructionsfrom the low power mode service to selectively deactivate elements thatare substantially unused for operation of the application during the lowpower mode.
 34. The apparatus of claim 32, further comprising a datastore accessible by the low power mode service to store informationindicative of the operating parameters.
 35. The apparatus of claim 32wherein the operating parameters can be provided to the low power modeservice by the BIOS.
 36. The apparatus of claim 32 wherein the operatingparameters can be provided to the low power mode service by theapplication.
 37. The apparatus of claim 32 wherein the operatingparameters include information indicative of a sequence in which theelements are to be deactivated based on operating dependencies betweensuch elements.
 38. The apparatus of claim 32 wherein the low power modeservice can selectively instruct deactivation of elements during the lowpower mode after use of such elements by the application for aparticular task.
 39. The apparatus of claim 32 wherein the instructionsfrom the low power mode service to selectively deactivate include atleast one suspend message to suspend at least one task that isirrelevant to operation of the application.
 40. The apparatus of claim32 wherein in response to a specific event, the low power mode servicecan generate a resume message to selectively resume at least some of thesuspended tasks.
 41. The apparatus of claim 32, further comprising a lowpower display module having a display screen on which data can bepresented by the application during the low power mode.